Hi Robert,
	We are data driving as much as we can.  That's actually the source of the dilemma.
	Here's a typical scenario.  Set up a "driving" test, we've found this works best for us.  That test calls a login test, Step A test, step b test, test C test step D test then log off test.
	Except for login test none of these tests can be run without some other test in front of then to leave you at a particular screen.  Leaving all these tests in one directory will lead to a terrible mix of tests that can be run alone and ones that can't.  A totally unworkable mess once we get more than a few tests going.  So, the driving tests need to be in one place and the others in some other place.  Ideally we would know which driving test calls which driven test, either based on organization or a feature that will tell us which tests are called by the given test.
	Thanks for your suggestion.
	Gregg.
	
	
	